Changes

Prepare the Tekton Catalog repository for agentic workflows.

• AGENTS.md: agent-oriented context file covering build/test commands, catalog conventions (TEP-0003, mandatory metadata, script interpolation security, versioning workflow), architecture, pattern references, and PR guidelines
• CLAUDE.md: symlink to AGENTS.md
• .claude/skills/: commit-message, code-review, running-tests, and task-authoring skills adapted for this project
• .claude/rules/: path-scoped rules for task YAMLs and test infrastructure
• .agents/skills: symlink to .claude/skills for agent auto-discovery
• .gitlint: commit message linting config (matches operator pattern)
• .pre-commit-config.yaml: gitlint + conventional-pre-commit hooks
• Makefile: lint, test, and setup targets
• .gitignore: add missing patterns
• README.md: add Quick Start section

agentready score

• 69.3/100 (Silver) — baseline assessment
• Remaining failures are out of scope for a YAML catalog repo (Python type annotations, pytest coverage, src/ layout)

Notes

• Skills validated against 30 recent merged PRs — covers the top activities: new task creation (37%), bug fixes (17%), maintenance (43%)
• Skills are adapted from the operator PR (tektoncd/operator#3387) and pruner PR (tektoncd/pruner#300), with
  catalog-specific scopes and examples

Submitter Checklist

These are the criteria that every PR should meet, please check them off as you
review them:

• Follows the authoring recommendations
• Includes docs (if user facing)
• Includes tests (for new tasks or changed functionality)
  • See the end-to-end testing documentation for guidance and CI details.
• Meets the Tekton contributor standards (including functionality, content, code)
• Commit messages follow commit message best practices
• Has a kind label. You can add one by adding a comment on this PR that
  contains /kind <type>. Valid types are bug, cleanup, design, documentation,
  feature, flake, misc, question, tep
• Complies with Catalog Organization TEP, see example. Note An issue has been filed to automate this validation

  • File path follows <kind>/<name>/<version>/name.yaml

  • Has README.md at <kind>/<name>/<version>/README.md

  • Has mandatory metadata.labels - app.kubernetes.io/version the same as the <version> of the resource

  • Has mandatory metadata.annotations tekton.dev/pipelines.minVersion

  • mandatory spec.description follows the convention

      ```
    
      spec:
        description: >-
          one line summary of the resource
    
          Paragraph(s) to describe the resource.
      ```
    

See the contribution guide for more details.